<h2>Why is this an issue?</h2>
<p>Calling a procedure with argument variables whose names match the procedure parameter names but in a different order can cause confusion. It could
indicate a mistake in the arguments' order, leading to unexpected results.</p>
<pre data-diff-id="1" data-diff-type="noncompliant">
Public Function Divide(divisor As Integer, dividend As Integer) As Double
    Return divisor / dividend
End Function

Public Sub DoTheThing()
    Dim divisor = 15
    Dim dividend = 5

    Dim result = Divide(dividend, divisor)  ' Noncompliant: arguments' order doesn't match their respective parameter names
    '...
End Sub
</pre>
<p>However, matching the procedure parameters' order contributes to clearer and more readable code:</p>
<pre data-diff-id="1" data-diff-type="compliant">
Public Function Divide(divisor As Integer, dividend As Integer) As Double
    Return divisor / dividend
End Function

Public Sub DoTheThing()
    Dim divisor = 15
    Dim dividend = 5

    Dim result = Divide(divisor, dividend) ' Compliant
    '...
End Sub
</pre>

